Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Migration to NX and refactor of Utils and Core into libraries. #4019

Open
wants to merge 32 commits into
base: main
Choose a base branch
from

Conversation

FrancescoMolinaro
Copy link
Contributor

@FrancescoMolinaro FrancescoMolinaro commented Feb 21, 2025

References

https://wiki.lyrasis.org/display/DSPACE/DSpace+Angular+%3A+library-based+architecture+proposal

Work includes also #3997 as we started from there to avoid future conflicts.

Description

This PR is a follow up of the migration to standalone components done in DSpace 8, with the goal of a modular architecture.

The new code serves two main purposes, first it introduces NX in the project as build orchestrator, second it introduces two new libraries: Core and Utils.

Instructions for Reviewers

The app needs to be running as before and the commands to run it remain unchanged.

List of changes in this PR:

  1. Migrated from an Angular CLI project to a NX standalone App.
    The Angular CLI has been replaced by the NX CLI.

  2. Created two new libraries Core and Utils:
    2.a Moved all data services and related models into Core.
    2.b Moved some of the states from AppState to CoreState to isolate the library.
    2.c Replaced in the whole library the environment import with injection token.

Checklist

This checklist provides a reminder of what we are going to look for when reviewing your PR. You do not need to complete this checklist prior creating your PR (draft PRs are always welcome).
However, reviewers may request that you complete any actions in this list if you have not done so. If you are unsure about an item in the checklist, don't hesitate to ask. We're here to help!

  • My PR is created against the main branch of code (unless it is a backport or is fixing an issue specific to an older branch).
  • My PR is small in size (e.g. less than 1,000 lines of code, not including comments & specs/tests), or I have provided reasons as to why that's not possible.
  • My PR passes ESLint validation using npm run lint
  • My PR doesn't introduce circular dependencies (verified via npm run check-circ-deps)
  • My PR includes TypeDoc comments for all new (or modified) public methods and classes. It also includes TypeDoc for large or complex private methods.
  • My PR passes all specs/tests and includes new/updated specs or tests based on the Code Testing Guide.
  • My PR aligns with Accessibility guidelines if it makes changes to the user interface.
  • My PR uses i18n (internationalization) keys instead of hardcoded English text, to allow for translations.
  • My PR includes details on how to test it. I've provided clear instructions to reviewers on how to successfully test this fix or feature.
  • If my PR includes new libraries/dependencies (in package.json), I've made sure their licenses align with the DSpace BSD License based on the Licensing of Contributions documentation.
  • If my PR includes new features or configurations, I've provided basic technical documentation in the PR itself.
  • If my PR fixes an issue ticket, I've linked them together.

FrancescoMolinaro and others added 24 commits February 5, 2025 18:33
…reState in tests files, move remote data utils into core
…r, move config (app) into core, move core states files into core folder, replace import of some constants for route paths with strings to avoid import/dependency from other part of the app
…r, move config (app) into core, move core states files into core folder, replace import of some constants for route paths with strings to avoid import/dependency from other part of the app
… of AppState + move notification state in core
@tdonohue tdonohue added dependencies Pull requests that update a dependency file new feature labels Feb 21, 2025
Copy link

Hi @FrancescoMolinaro,
Conflicts have been detected against the base branch.
Please resolve these conflicts as soon as you can. Thanks!

@atarix83 atarix83 self-assigned this Feb 26, 2025
@pcg-kk pcg-kk self-requested a review February 27, 2025 15:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Pull requests that update a dependency file merge conflict new feature
Projects
Status: 👀 Under Review
Development

Successfully merging this pull request may close these issues.

4 participants